Skip to content

Bump qltysh/qlty-action/coverage from 2.5.0 to 2.6.0 - #982

Merged
happy5214 merged 1 commit into
mainfrom
dependabot/github_actions/main/qltysh/qlty-action/coverage-2.6.0
Nov 16, 2026
Merged

happy5214 merged 1 commit into
mainfrom
dependabot/github_actions/main/qltysh/qlty-action/coverage-2.6.0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 16, 2026

Copy link
Copy Markdown
Contributor

Bumps qltysh/qlty-action/coverage from 2.5.0 to 2.6.0.

Release notes

Sourced from qltysh/qlty-action/coverage's releases.

v2.6.0

Fixed

  • The coverage action now redacts the coverage token from the Qlty CLI output included in error messages, so the token is masked everywhere the message is reported, including Sentry. This applies to project, workspace and OIDC tokens (#221)
Changelog

Sourced from qltysh/qlty-action/coverage's changelog.

Changelog

v2.7.0 (2026-11-14)

New

  • The coverage and fmt actions now accept a telemetry input (default true). Set it to false, or set QLTY_TELEMETRY: off in the job environment, to skip error reporting and turn off telemetry in the Qlty CLI (#225)

Improved

  • When an action reports an error, it now sends only the error class, a fixed failure kind, the Qlty CLI exit code, the action name and version, and the OS and Node.js version. Stack traces, CLI output, the repository name, run URL, commit SHA, runner hostname, timezone and traces are no longer sent, and successful runs send nothing (#225)
  • The warning shown when the Qlty CLI's attestation check is skipped now explains that the unverified CLI runs with access to the job's tokens and secrets, says why the check was skipped, and links to the docs (#226)
  • The fmt action's failure message now says why it failed, such as the CLI exit code or a download error (#225)

Fixed

  • The coverage action on an unsupported platform now fails the step when skip-errors: false, instead of passing after logging the error (#225)

v2.6.0 (2026-11-13)

Fixed

  • The coverage action now redacts the coverage token from the Qlty CLI output included in error messages, so the token is masked everywhere the message is reported, including Sentry. This applies to project, workspace and OIDC tokens (#221)

v2.5.0 (2026-10-23)

Improved

  • The Qlty CLI must now pass its attestation check before it runs. If no attestation matches the downloaded CLI, or the check rejects it, the step fails, including in the coverage action with skip-errors: true. Pinning cli-version to a release older than 0.555.0, which have no attestation, now fails; remove cli-version or set a current release (#212)
  • When the attestation check cannot finish because GitHub or Sigstore is unavailable, the coverage action follows skip-errors: with skip-errors: true it logs the error and passes the step without running the CLI. The install and fmt actions fail (#216)
  • The attestation check needs GitHub CLI (gh) 2.67.0 or later. Without a usable gh, as on many self-hosted runners and container: jobs, the actions log a warning that the run is unverified and continue (#212)
  • The attestation lookup always goes to github.com, even when GH_HOST points at GitHub Enterprise; in that case set github-token to a github.com token (#212)

v2.4.0 (2026-09-24)

Fixed

  • Security updates to bundled dependencies (#207, #208, #209)

v2.3.0 (2026-07-09)

New

  • Add a selected input to the coverage action for marking an upload as covering a selected subset of the test suite, which contributes to diff coverage only and is excluded from total coverage (#200)

v2.2.3 (2026-07-07)

  • Internal release process improvements (no user-facing changes) (#196)

v2.2.2 (2026-07-07)

... (truncated)

Commits
  • 357cd88 Prepare release v2.6.0 (#223)
  • 7ff1add Fix coverage typecheck, share one strict tsconfig, and add required test chec...
  • 8e2aa05 Redact the coverage token from CLI output in errors (#221)
  • 79a913e chore: add Claude Code Review instructions (#220)
  • a70c261 ci: scope the qlty-releases App token and gate it behind an environment (#218)
  • See full diff in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [qltysh/qlty-action/coverage](https://github.com/qltysh/qlty-action) from 2.5.0 to 2.6.0.
- [Release notes](https://github.com/qltysh/qlty-action/releases)
- [Changelog](https://github.com/qltysh/qlty-action/blob/main/CHANGELOG.md)
- [Commits](qltysh/qlty-action@ebcd284...357cd88)

---
updated-dependencies:
- dependency-name: qltysh/qlty-action/coverage
  dependency-version: 2.6.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code labels Nov 16, 2026
@happy5214
happy5214 merged commit 0cc7191 into main Nov 16, 2026
13 checks passed
@dependabot
dependabot Bot deleted the dependabot/github_actions/main/qltysh/qlty-action/coverage-2.6.0 branch November 16, 2026 17:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant